[WRONG BRANCH] fix(auth): prefer exact accountId match when importing OAuth identities - #271
Closed
luvs01 wants to merge 1 commit into
Closed
[WRONG BRANCH] fix(auth): prefer exact accountId match when importing OAuth identities#271luvs01 wants to merge 1 commit into
luvs01 wants to merge 1 commit into
Conversation
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
✅ Deterministic PR hygiene checks passed. |
⏳ DRAFT
What to do
Its title has been prefixed with |
Owner
Author
|
@coderabbitai review |
✅ Action performedReview finished.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
accountIdcould update an earlier legacy email-only row (if that row appeared earlier in the accounts list) and leave a separate stableaccountIdrow, producing duplicate/stale rows.accountIdmatch across the account set.Description
upsertCredentialByIdentityinsrc/oauth/store.tsto prefer an exactaccountIdmatch across the entire account set whensafe.accountIdis present, and only then fall back to an email-only match; introduced amatchesEmailOnlyhelper and an ordered lookup.accountId(no functional change for those code paths).tests/account-import.test.tsthat seeds anauth.jsonwith an earlier email-only legacy row and a later stableaccountIdrow and verifies the exactaccountIdrow is updated while the legacy row remains unchanged.Testing
bun test tests/account-import.test.ts, which passed (19 tests, 0 failures).bun run typecheckandbun run privacy:scan, both succeeded.bun run test), but the run hit unrelated environment/network failures and timeouts in other integration tests (external package fetches and some test timeouts), so the full-suite run could not complete; the focused regression test and typecheck/privacy checks validate the fix for this change.Codex Task
Summary by CodeRabbit
Bug Fixes
Tests